Private cloud routing server, private network service and smart device client architecture without utilizing a public cloud based routing server

ABSTRACT

A method and system for use with a public cloud network is disclosed, wherein the public cloud network includes at least one private cloud routing server, at least one private network service and at least one smart device client in communication therewith. The method and system comprise setting up the at least one private cloud routing server, the at least one private network service and the at least one smart device client in a client server relationship. The at least one private cloud routing server includes a message box associated therewith. The first message box is located in the public network. The at least one smart client includes a second message box associated therewith. The second message box is located on the public network. The method includes passing session based message information between the at least one private cloud routing server and the at least one smart device client via the first message box and the second message box in a secure manner. The session based information is authenticated by the private cloud routing server and the at least one smart device client. The smart device client and the private cloud routing server can then communicate with each other after the session based information is authenticated. The at least one private network service is then manageable and accessible by the at least one smart device client from anywhere at anytime without utilizing a public cloud based routing server.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation-in-part of U.S. patent applicationSer. No. 13/229,285, filed Sep. 9, 2011, entitled “PRIVATE CLOUD SERVERAND CLIENT ARCHITECTURE WITHOUT UTILIZING A ROUTING SERVER,” which isincorporated herein by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to networking and moreparticularly to the use of private cloud networks.

BACKGROUND OF THE INVENTION

In the Internet connected environment, the Smart Device Clientsincluding smart phone, tablet, eBook reader, notebook, PC and varioussmart gadgets are ubiquitous and omnipresent. Other than connectivity,one of the values of the Smart Device Clients is to be able to connectat any time and any place to retrieve services from one or many servingparties or servers. The services include audio, video contents, live orarchived information, and execution of applications, social media,messaging, email, storage, backup, calendar, contact, synchronizationand others. There are different types of servers that serve thesevarious requests from the Smart Device Clients. In general, these typesof servers can be categorized to fall into two groups: a public cloudand a private cloud. Servers in the public cloud, implied by the name“public”, provide services that tend to be free with limitedfunctionality or fee-based with more sophisticated services and interactwith the public. Examples of the public cloud server include datacenter, social media services and storage/content provider through theInternet. On the other hand, servers in the private cloud tend toaddress the private need. The services provided are more private andpersonal as opposed to those offered by the public cloud.

One example of the application of the private cloud server is a privatecloud storage server (PCSS). The PCSS sits within the local area network(LAN) managed by the user. It provides on-line and backup storage forthe user either within the LAN or in the wide area network (WAN). Theuser is able to use a Smart Device Client to access information withinthe private cloud storage server at anytime from anywhere. The privatecloud storage server and the associated Smart Device Client thereforeform an example of the Private Cloud Server and Client architecture.

Conventionally, there are many storage server solutions, includingnetwork attached storage (NAS), Windows/Mac/Linux server, and directattached storage (DAS) to fulfill the PCSS requirement. But thechallenge for the Smart Device Clients in the field has been how toavoid the cumbersome setup to penetrate the firewall behind the routeron the LAN to access the PCSS in a home or office environment. There areat least four kinds of solutions to this challenge.

One solution is to assign a fixed IP address and open certain ports forthe router in front of the PCSS, such that the Smart Device Client isable to locate the PCSS from outside the LAN and to authenticate itself,penetrate the firewall and establish a secure communication channel withthe PCSS.

The second solution applies when a fixed IP address is not available.The user configures the LAN router of the PCSS and opens certain portsto map to the PCSS. The router is therefore able to be located by theintended Smart Device Client through a dynamic DNS (DDNS) service on theWAN. The Smart Device Client can authenticate itself, penetrate thefirewall and establish a secure communication channel with the PCSS.

The third solution is to rely on another routing server in the WAN toconduct the virtual private network (VPN) communication between theSmart Device Client and the PCSS. The VPN communication allows the SmartDevice Client to locate the PCSS, authenticate itself, penetrate thefirewall and establish a secure communication channel with the PCSS.

The fourth solution is to rely on another routing server in the WAN toconduct the remote desktop protocol (RDP) or virtual network computing(VNC) communication between the Smart Device Client and the PCSS. TheRDP/VNC communication allows the Smart Device Client to locate the PCSS,authenticate itself, penetrate the firewall and establish a securecommunication channel with the PCSS. Other solutions can be mix- andmatch of the above mentioned solutions.

In the first scenario, a fixed IP address is required and the routerneeds to be set up and configured. The down side is that a fixed IPinvolves more cost and is usually not available in the home and smallbusiness environment. The router set up and configuration can be verycomplicated and are not user friendly with most consumers.

In the second scenario, a DDNS service is required and the router needsyet more complex set up. Again, the DDNS set up involves additional costand complexity into the system. The router set up and configuration canbe very complicated and is not user friendly with most consumers.

In the third and fourth scenarios, an outside routing server or serviceneeds to be established, while a router set up is not necessary. Theoutside routing server or service controls and handleslogin/authentication between the Smart Device Client and the server. Theprivate cloud becomes less private and less secure through the publiccloud based server or service. If for any reason the server or serviceis down, the communication and availability of the private cloud storageserver will be jeopardized.

All of these scenarios require technical expertise that may be suitablefor conventional corporate environment, but these scenarios are notsuitable for consumer oriented Smart Device Client centric deployment.

In most conventional systems, an outside or public cloud based routingserver is used by the Smart Device Client during access to the PrivateCloud Server. Using an outside server creates a number of concerns tothe Smart Device Client owner.

First, the sense of trust is always in question, because the outside orpublic cloud based routing server is a middleman during allcommunication transactions between the Smart Device Client and thePrivate Cloud Server. It may hold all user account info, password andtheir corresponding IP addresses of the Smart Device Client and thePrivate Cloud Server. The routing server is able to sniff anycommunication in-between and render it insecure.

Second, being an outside and public cloud based routing server, itsbusiness model may not always be in-line or in-sync with the SmartDevice Client owner. If the routing server is out of service due to anybusiness reason, there is no remedy or option of replacement to restorethe service. The routing server potentially poses a tremendous businessrisk to the user as the vital link in the communication can be brokenwithout recourse.

Accordingly, what is needed is a system and method that addresses theabove identified issues. The present invention addresses such a need.

SUMMARY OF THE INVENTION

A method and system for use with a public cloud network is disclosed,wherein the public cloud network includes at least one private cloudrouting server, at least one private network service and at least onesmart device client in communication therewith. The method and systemcomprise setting up the at least one private cloud routing server, theat least one private network service and the at least one smart deviceclient in a client server relationship. The at least one private cloudrouting server includes a message box associated therewith. The firstmessage box is located in the public network. The at least one smartclient includes a second message box associated therewith. The secondmessage box is located on the public network.

The method includes passing session based message information betweenthe at least one private cloud routing server and the at least one smartdevice client via the first message box and the second message box in asecure manner. The session based information is authenticated by theprivate cloud routing server and the at least one smart device client.The smart device client and the private cloud routing server can thencommunicate with each other after the session based information isauthenticated. The at least one private network service is thenmanageable and accessible by the at least one smart device client fromanywhere at anytime without utilizing a public cloud based routingserver.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of a conventional Cloud NetworkInfrastructure.

FIG. 1B is a block diagram of a Cloud Network Infrastructure inaccordance with an embodiment.

FIG. 2 shows a conventional implementation of how the Private CloudServer can be accessed physically through the configuration of itsRouter_P on the LAN.

FIG. 3 shows a conventional implementation of how the Private CloudServer can be accessed logically through registration with a VPN RoutingServer.

FIG. 4 shows an implementation of how the Private Cloud Server can beaccessed logically through registration with an Intermediate RoutingServer.

FIG. 5 shows a conventional implementation of how the Private CloudServer can be accessed logically through peer-to-peer communicationregistering with an Intermediate Routing Server.

FIG. 6 illustrates an Initial Setup of the Private Cloud Server RoutingServer and the Smart Device Client in accordance with the presentinvention.

FIG. 7 shows the communication flow of the Smart Device Client inaccordance with the present invention.

FIG. 8 shows the communication flow of the Private Cloud Routing Serverin accordance with the present invention.

FIG. 9 shows a block diagram of the Private Cloud Routing Server inaccordance with the present invention.

FIG. 10 shows a block diagram of the Smart Device Client in accordancewith the present invention.

DETAILED DESCRIPTION

The present invention relates generally to networking and moreparticularly to the use of private cloud networks. The followingdescription is presented to enable one of ordinary skill in the art tomake and use the invention and is provided in the context of a patentapplication and its requirements. Various modifications to theembodiments and the generic principles and features described hereinwill be readily apparent to those skilled in the art. Thus, the presentinvention is not intended to be limited to the embodiments shown, but isto be accorded the widest scope consistent with the principles andfeatures described herein.

The term “Client” is interchangeable with “Smart Device Client”throughout discussion in the context. The term “router” is in generalinterchangeable with “gateway”, “access point” and/or “NAT” (networkaddress translation) in the discussion.

A system and method in accordance with the present invention addressesthe following challenges in a consumer oriented environment for a SmartDevice Client in a WAN to be able to obtain services from a PrivateCloud Storage Server (PCSS) or any Private Cloud Server (PCS):

1. Access the Private Cloud Server (PCS) at anytime from anywhere.

2. Access the PCS behind the firewall with fixed or dynamic IP address.

3. Require no outside or public cloud based routing server in the WAN.

4. Require no additional router setup in the LAN.

5. Authenticate with the PCS.

6. Establish a secure communication channel with the PCS.

If such challenges can be met and resolved, it will increase thedeployment of the Private Cloud Server or service exponentially, due tothe plug and play simplicity and availability. It also removes thetechnical and business concern by not utilizing a public cloud basedrouting server. The Private Cloud Server covering storage, remotedesktop service and Internet of Things (IoT) becomes very affordable andubiquitous in the private cloud infrastructure.

In the private cloud environment, if there are more than one privatecloud servers or services co-exist at the same time, it is advantageousto separate out the functions of Private Cloud Server into twofunctional blocks including Private Cloud Routing Service and PrivateNetwork Service. The Private Network Service (PNS) by itself is designedto be managed and accessed on the private network environment, be itwired or wireless, by the Smart Device Client. Examples of the PrivateNetwork Service include application program server to provide remotedesktop protocol (RDP), VNC, office tools, media player, and other userspecific applications. It may also function as a storage server thatcontains multiple terabytes of storage serving the private cloud. ThePrivate Cloud Routing Service functions of the multiple Private CloudServers can then be aggregated together into just one Private CloudRouting Server (PCRS). The Private Cloud Routing Server can generally bereferred to as a Private Cloud Router.

A system and method in accordance with the present invention addressesthe following challenges in the consumer oriented environment forutilizing the Smart Device Client in the WAN to be able to manage andaccess Private Network Service (PNS) from a Private Cloud Routing Server(PCRS):

1. Access the Private Cloud Routing Server (PCRS) at anytime fromanywhere.

2. Access the PCRS behind the firewall with fixed or dynamic IP address.

3. Require no outside or public cloud based routing server in the WAN.

4. Require no additional router setup in the LAN.

5. Authenticate with the Private Cloud Routing Server (PCRS).

6. Establish a secure communication channel with the Private NetworkService (PNS) to manage and access.

If the Private Cloud Routing Server (PCRS) can fulfill the abovementioned challenges, the heterogeneous Private Cloud Servers fromdifferent manufacturers and vendors can then be broken down into simplerPrivate Network Services and remove the complexity of private cloudsetup, configuration and access

The purpose of a system and method in accordance with the invention isto provide a Private Cloud Routing Server (PCRS), Private NetworkService and Client architecture without utilizing a routing server. Thesystem and method in accordance with the present invention addresses theabove identified challenges that to allow a Client to be able to accessthe Private Network Service (PNS) from anywhere at anytime. The systemand method also accesses the PNS behind a firewall with fixed or dynamicIP, requires no additional router setup and no public cloud basedrouting server in the WAN, to authenticate with the PCRS, and toestablish a secure communication channel directly with the PNS.

As shown in FIG. 1A, a cloud network infrastructure includes a publiccloud 100, a public cloud server 113, an intermediate routing server112, a VPN routing server 114, a Smart Device Client 101 in the WAN, aRouter_P 102 and a Router_S 103. The Router_S 103 connects between a LAN105 and the Internet in public cloud 100. The Router_P 102 connectsbetween a LAN 104 and the Internet in public cloud 100. Behind the LAN104, there are Smart Device Clients 106, 107 and a Private Cloud Server(PCS) 108. Behind the LAN 105, there are Smart Device Clients 109, 110and 111. The Smart Device Client can be a PC, notebook, tablet, eBookreader, GPS, smart TV, set top box, MP3 player, or any networkableembedded device.

They are denoted in the Cloud Network Infrastructure as 101, 106, 107,109, 110, and 111. Any one of the Smart Device Clients above isinterchangeable in the context and discussion. The focus on thisdiscussion is the Smart Device Client 109, as the representative in thiscontext.

Physically, there are three scenarios that a Smart Device Client 101,107 or 109 can connect to the Private Cloud Server 108. First, a SmartDevice Client 107 determines whether the target is in the locallyaccessible LAN 104 and decides to connect to the Private Cloud Server108 directly. Second, the Smart Device Client 101 determines the targetis not in the locally accessible LAN 104 and decides to connect throughthe WAN to the public cloud 100. The WAN locates the Router_P 102 andLAN 104, then connects to the Private Cloud Server 108. Third, the SmartDevice Client 109 determines the target is not in the locally accessibleLAN 105 and decides to passes through LAN 105, Router_S 103, andconnects to the public cloud 100 in the WAN.

The Smart Device Client 109 then locates Router_P 102, LAN 104 andconnects to the Private Cloud Server 108. The first and the secondscenario are two special cases and derivatives of the third scenario.Therefore, it is beneficial to focus on the third scenario that isbroader in scope and complexity.

FIG. 2 shows a conventional implementation of how the Private CloudServer 108 can be accessed physically through the configuration of itsRouter_P 102 on the LAN 104. There are two steps involved in configuringthe Router_P 102. First, the user needs to map the private IP address ofthe Private Cloud Server 108, to a specific port in Router_P 102, as instep 200. Second, the user needs to register the public IP address ofthe Router_P 102 that hosts the Private Cloud Server 108, with anIntermediate Routing Server 112 in the WAN, as in step 201. Before theSmart Device Client 109 can access the Private Cloud Server 108, itlooks up the Intermediate Routing Server 112 to locate the public IPaddress of the Private Cloud Server 108, as in step 202. It then canstart accessing, as in step 203, the predetermined port of the Router_P102, which is correctly mapped to the private IP address of the PrivateCloud Server 108.

The configuration of the Router_P 102 and the setup of the IntermediateRouting Server 112 are not really trivial and can be very difficult formost of the end users. Further, by mapping the private IP address of thePrivate Cloud Server 108 to a port that is directly and permanentlyaddressable by the outside world, it conceivably creates a big securityrisk for the Private Cloud Server 108.

The Private Cloud Server 108 is directly and permanently exposed to theoutside world that can invite many vicious attacks. Also, theIntermediate Routing Server 112 is a public cloud based server. Itcreates a number of concerns to the Smart Device Client 109 owner.First, the sense of trust is always in question, because theIntermediate Routing Server 112 is a middleman during all communicationtransactions between the Smart Device Client 109 and the Private CloudServer 108. It may hold all user account information, password and theircorresponding IP addresses of the Smart Device Client 109 and thePrivate Cloud Server 108. The Intermediate Routing Server 112 is able tosniff any communication in-between and render it insecure.

Second, being an outside and public cloud based routing server, thebusiness model of the Intermediate Routing Server 112 may not always bein-line or in-sync with the Smart Device Client 109 owner. If theIntermediate Routing Server 112 is out of service due to any businessreason, there is no remedy or option of replacement to restore theservice. It potentially poses a tremendous business risk to the user, asthe vital link in the communication can be broken without recourse.

FIG. 3 shows a conventional implementation of how the Private CloudServer 108 can be accessed logically through registration with a VPNRouting Server 114. During setup of a virtual private network, thePrivate Cloud Server 108 first registers its public IP address and itsprivate IP address with a VPN (virtual private network) Routing Server114 and stays logging in, as in 300. The Smart Device Client 109 alsoregisters its public IP address and its private IP address with the sameVPN Routing Server 114, in step 301. The VPN Routing Server 114allocates virtual IP addresses for both Private Cloud Server and theSmart Device Client 109 and sets up a Virtual Private Network 302. Bythis time, the Smart Device Client 109 and the Private Cloud Server 108are in the same virtual IP domain under the control of the VPN RoutingServer 114. All communication between the Smart Device Client 109 andthe Private Cloud Server 108 are encapsulated under the VPN protocol.

The Smart Device Client 109 then logs in to the VPN Routing Server 114and looks up the virtual IP address of the Private Cloud Server 108, instep 303. All communication between the Smart Device Client 109 and thePrivate Cloud Server 108 are intercepted and encapsulated by the VPNRouting Server 114, in step 304. The Smart Device Client 109 can thenstart accessing the Private Cloud Server 108, as in step 305.

As opposed to the approach disclosed in FIG. 2, the VPN Routing Serverapproach benefits by eliminating the router configuration. It thereforemakes the setup much easier for the user. But it suffers the same, ifnot more serious business concerns on the issue of having to have allcommunication going through a public cloud based routing server. Being apublic cloud based server, the VPN Routing Server 114 creates a numberof concerns to the Smart Device Client 109 owner. First, the sense oftrust is always in question, because the VPN Routing Server 114 is amiddleman during all communication transactions between the Smart DeviceClient 109 and the Private Cloud Server 108. It may hold all useraccount information, password and their corresponding IP addresses ofthe Smart Device Client 109 and the Private Cloud Server 108. The VPNRouting Server 114 is able to sniff any communication in-between andrender it insecure. Second, being an outside and public cloud basedrouting server, the business model of the VPN Routing Server 114 may notalways be in-line or in-sync with the Smart Device Client 109 owner. Ifthe VPN Routing Server 114 is out of service due to any business reason,there is no remedy or option of replacement to restore the service.Unless the user has total control over the VPN routing server, itpotentially poses a tremendous business risk to the user, as the vitallink in the communication can be broken without recourse.

FIG. 4 shows an implementation of how the Private Cloud Server 108 canbe accessed logically through registration with an Intermediate RoutingServer 112. The Private Cloud Server 108 first registers its public IPaddress and its private IP address with an Intermediate Routing Server112 and obtains a set of ID and Password from the server, in step 400.The Smart Device Client 109 then registers its public IP address and itsprivate IP address with the same Intermediate Routing Server 112 andobtains a set of ID and Password, as in step 401. The Private CloudServer 108 logs in to the Intermediate Routing Server 112, as in step402.

Before the Smart Device Client 109 is able to access the Private CloudServer 108, a number of steps have to happen. First, the Smart DeviceClient 109 obtains the ID and Password of the Private Cloud Server 108from the server through a secure channel, such as phone call, email,text message or snail mail, as in step 403. The Smart Device Client 109then logs in to the Intermediate Routing Server 112 with its own ID andthe obtained ID and Password of the Private Cloud Server 108, as in step404. All communication between the Smart Device Client 109 and thePrivate Cloud Server 108 are intercepted and encapsulated by theIntermediate Routing Server 112, as in step 405. Finally, the SmartDevice Client 109 can start accessing the Private Cloud Server 108, asin step 406.

As opposed to the conventional approach shown in FIG. 2, theIntermediate Routing Server approach benefits from doing away with therouter configuration. It therefore makes the setup much easier for theuser. But it suffers the same, if not more serious business concerns onthe issue of having to have all communication going through a publiccloud based routing server.

Being a public cloud based server, the Intermediate Routing Server 112creates a number of concerns to the Smart Device Client 109 owner.First, the sense of trust is always in question, because theIntermediate Routing Server 112 is a middleman during all communicationtransactions between the Smart Device Client 109 and the Private CloudServer 108. It may hold all user account information, password and theircorresponding IP addresses of the Smart Device Client 109 and thePrivate Cloud Server 108. The Intermediate Routing Server 112 is able tosniff any communication in-between and render it insecure.

Second, being an outside and public cloud based routing server, thebusiness model of the Intermediate Routing Server 112 may not always bein-line or in-sync with the Smart Device Client 109 owner. If theIntermediate Routing Server 112 is out of service due to any businessreason, there is no remedy or option of replacement to restore theservice. It potentially poses a tremendous business risk to the user, asthe vital link in the communication can be broken without recourse.

FIG. 5 shows an implementation of how the Private Cloud Server 108 canbe accessed logically through peer-to-peer communication registeringwith an Intermediate Routing Server 112. The Private Cloud Server 108first registers its public IP address and its private IP address with anIntermediate Routing Server 112 and obtains a set of ID and Passwordfrom the server, in step 500. The Smart Device Client 109 then registersits public IP address and its private IP address with the sameIntermediate Routing Server 112 and obtains a set of ID and Password, asin step 501. The Private Cloud Server 108 and the Smart Device Client109 log in to the Intermediate Routing Server 112, as in step 502.

Before the Smart Device Client 109 is able to access the Private CloudServer 108, a number of steps have to happen. First, the Smart DeviceClient 109 and the Private Cloud Server 108 obtain the public IP andprivate IP addresses of the other party from the Intermediate RoutingServer, as in step 503. Both parties punch a hole in their respectiverouters during initial outgoing communication attempt with each other,as in step 504. All communication between the Smart Device Client 109and the Private Cloud Server 108 are bound together, establishing apeer-to-peer communication channel in between, as in step 505. Finally,the Smart Device Client 109 can start accessing the Private Cloud Server108, as in step 506.

As opposed to the conventional approaches of FIG. 2, FIG. 3 and FIG. 4,the Intermediate Routing Server approach of this embodiment has thebenefit of establishing peer-to-peer communication between the clientand the server and offers better performance. But it still suffers fromthe problem of “single point of failure” where all communication gothrough a single public cloud based routing server. Being a public cloudbased server, the Intermediate Routing Server 112 creates a number ofconcerns to the Smart Device Client 109 owner. First, the sense of trustis always in question, because the Intermediate Routing Server 112 is amiddleman holding all user account information, password and theircorresponding IP addresses of the Smart Device Client 109 and thePrivate Cloud Server 108.

Second, being an outside and public cloud based routing server, thebusiness model of the Intermediate Routing Server 112 may not always bein-line or in-sync with the Smart Device Client 109 owner. If theIntermediate Routing Server 112 is out of service due to any businessreason, there is no remedy or option of replacement to restore theservice. It potentially poses a tremendous business risk to the user, asthe vital link in the communication can be broken without recourse.

One of the biggest advantages of a system and method in accordance withthe present invention over the above cited conventional approaches is toeliminate with the role of the public cloud based routing server duringaccess, as in the case of either the VPN Routing Server or theIntermediate Routing Server. Another advantage of the invention is thatno secret information such as password of the account is ever exchangedbetween the Smart Device Client 109 and the Private Cloud Server 108.

FIG. 1B is a block diagram of a Cloud Network Infrastructure inaccordance with an embodiment. Those elements that are the same as thosedescribed with respect to FIG. 1A have the same designators. However, inthis embodiment, there are also two message boxes, Client Message Boxmessage_box_S 115 and Routing Server Message Box message_box_P 116 whichpurposes will be described in detail hereinafter.

As in FIG. 1A, behind the LAN 104, there are Smart Device Clients 106,107, a Private Cloud Server Routing Server (PCRS) 108 and a PrivateNetwork Service (PNS) 128. The original Private Cloud Server (PCS) 108in FIG. 1A has been changed to a Private Cloud Routing Server (PCRS) 108and a Private Network Service 128 (PNS) in FIG. 1B. Behind the LAN 105,there are Smart Device Clients 109, 110 and 111. The Smart Device Clientcan be a PC, notebook, tablet, eBook reader, GPS, smart TV, set top box,MP3 player, or any networkable embedded device. They are denoted in theCloud Network Infrastructure as 101, 106, 107, 109, 110, and 111. Anyone of the Smart Device Clients above is interchangeable in the contextand discussion. The focus on this discussion is the Smart Device Client109, as the representative in this context.

To describe the features of the present invention in more detail, refernow to FIG. 6, FIG. 7 and FIG. 8, which cover the initial setup phaseand the access phase of the invention.

FIG. 6 illustrates an Initial Setup of the Private Cloud Routing Server108 and the Smart Device Client 109 in accordance with the presentinvention. The Private Cloud Routing Server 108 and the Smart DeviceClient 109 form a server-client relationship. The Private Cloud RoutingServer 108 first creates an authorized client list with the clientaccount name and the corresponding message box information. The messagebox information can be in the form of an email account, text messageaccount or other unique public account information of the client.

On the Private Cloud Routing Server 108 side, it sends a session basedinvitation to message_box_S 115 of the intended Smart Device Client 109as one of the authorized users, in step 601. The session basedinvitation may include the routing server message box addressmessage_box_P 116. The Private Cloud Routing Server 108 then attempts toretrieve session based access request that includes the client messagebox address message_box_S 115, client public IP Public_IP_S119 andprivate IP private_IP_S120 addresses from the routing server message boxmessage_box_P 116, as in step 602.

If the access request is invalid, then it loops back to step 601. If theaccess request is valid, the Private Cloud Routing Server 108 thenregisters the client message box 115, public IP 119 and the private IP120 addresses of the Smart Device Client 109, as in step 604. ThePrivate Cloud Routing Server 108 sends to the client message boxmessage_box_S 115, a session based acknowledgement with its currentrouting server public IP and private IP addresses, public_IP_P 117 andprivate_IP_P 118, as in step 605. The Private Cloud Routing Server 108can start the communication request to the Smart Device Client 109, asin step 606.

On the Smart Device Client 109 side, it first retrieves the sessionbased invitation from its own message_box_S 115, as in step 611. Thesession based invitation includes the message box address message_box_P116 of the Private Cloud Routing Server. If the invitation from thePrivate Cloud Routing Server 108 is invalid, then it loops back to step611. If the invitation is valid from the Private Cloud Routing Server108, the Smart Device Client 109 may reply to the Private Cloud RoutingServer 108 message box message_box_P 116 with a session based accessrequest, to register its current client message box address, public IPand private IP addresses whenever it needs to access to the PrivateCloud Routing Server 108, as in step 613. The session based accessrequest may include the Smart Device Client 109 message box address,message_box_S 115, and the client public and private IP addresses,public_IP_S 119 and private_IP_S 120. The Smart Device Client 109 thenretrieves from the client message_box_S 115, the session basedacknowledgement with the Private Cloud Routing Server current public IPand private IP addresses, public_IP_P 117 and private_IP_P 118, as instep 614. The Smart Device Client 109 can start the communicationrequest to the Private Cloud Routing Server, as in step 615. These twoindependent processes conclude the initial setup of the Private CloudRouting Server 108 and the Smart Device Client 109.

The message box servers, hosting either server or client message boxes,can be an email server, text message server, or any kind of server thatcan host secure message for information exchange between the PrivateCloud Routing Server 108, as a server, and the Smart Device Client 109,as a client. The security and business model of the message box serveris well understood and expected in the industry by the user. For anyreason the message box server is down, it can be replaced or redeployedimmediately without jeopardizing the communication between the serverand the client in the private cloud infrastructure.

FIG. 7 shows the communication flow of the Smart Device Client 109 inaccordance with the present invention. The Smart Device Client 109 canstart peer-to-peer communication with the Private Cloud Routing Server108 without going through an Intermediate Routing Server 112 or a VPNRouting Server 114. The Smart Device Client 109 first sends acommunication request passing through its Router_S 103 to the Router_P102 of the Private Cloud Routing Server 108, as in step 700. TheRouter_S 103 registers the public IP and private IP addresses of theSmart Device Client 109 and the Private Cloud Routing Server 108, as instep 701. The Router_S 103 outgoing route stays open, punching a holeand waiting for response from the Private Cloud Routing Server 108, asin step 702. The Router_S 103 then checks if the incoming response isfrom the Private Cloud Routing Server 108, as in step 703. If theincoming response is invalid and it has timed out, then theinitialization process of the Smart Device Client 109 starts over again,as in step 708. If it has not timed out, then it loops back to step 702.But, if the incoming response is valid, the Router_S 103 will bind theincoming public IP address and the private IP address of the PrivateCloud Routing Server 108, with the registered outgoing private IPaddress of the Smart Device Client 109, as in step 704. The incomingrequest from the Private Cloud Routing Server 108 is then routed to theSmart Device Client 109, as in step 705. The Smart Device Client 109 canstart secure peer-to-peer communication with the Private Cloud RoutingServer 108 and access services from it, as in step 706.

FIG. 8 shows the communication flow of the Private Cloud Routing Server108 in accordance with the present invention. The Private Cloud RoutingServer 108 can start peer-to-peer communication with the Smart DeviceClient 109 without going through an Intermediate Routing Server 112 or aVPN Routing Server 114. The Private Cloud Routing Server 108 first sendsa communication request passing through its Router_P 102 to the Router_S103 of the Smart Device Client 109, as in step 800. The Router_P 102, inresponse to the outgoing communication request, then registers thepublic IP and private IP addresses of the Smart Device Client 109 andthe Private Cloud Routing Server 108, as in step 801. The Router_P 102outgoing route stays open, punching a hole and waiting for response fromthe Smart Device Client 109, as in step 802. The Router_P 102 checks forincoming response to see if it is from the Smart Device Client 109, asin step 803. If the incoming response is invalid and it has timed out,then the initialization process of the Private Cloud Routing Server 108starts over again, as in step 808. If it has not timed out, then itloops back to step 802. But, if the incoming response is valid, theRouter_P 102 will bind the incoming public IP address and the private IPaddress of the Smart Device Client 109, with the registered outgoingprivate IP address of the Private Cloud Routing Server 108, as in step804. The incoming request from the Smart Device Client 109 is thenrouted to the Private Cloud Routing Server 108. The Private CloudRouting Server 108 can start secure peer-to-peer communication with theSmart Device Client 109 and accept access of services from it, as instep 806.

In order to ensure the peer-to-peer communication channel secure, anumber of security measures are deployed, including AES encryptionand/or SSL (secure socket layer), TLS (transport layer security). Thesession based communication between the server and client, includinginvitation, access request and acknowledgement, also utilizes randomnumber seeds, time stamp, encryption and hashing to defeat man-in-themiddle and reply attack from the public cloud based to ensure thesecurity and integrity of the communication.

Because the invention does not rely on a public cloud based routingserver, it solves and eases a number of concerns to the Smart DeviceClient owner. First, there is no single point of failure between theclient and the server. Second, there is no middleman during anycommunication transactions between the Smart Device Client 109 and thePrivate Cloud Routing Server 108. The performance is therefore better.Third, no sniffing of any communication in-between is possible andtherefore makes the process very secure for the client and server. Theuser account information, password and their corresponding IP addressesof the Smart Device Client 109 and the Private Cloud Routing Server 108are never exposed to a public cloud based. The only outsidecommunication channels utilized in information exchange between theSmart Device Client 109 and the Private Cloud Routing Server 108 are thetwo private message boxes message_box_S 115 and message_box_P 116. Thepassword information is never exchanged between the Private CloudRouting Server 108 and the Smart Device Client 109, as a client. Thesecurity of the communication is as good as the message box servershosting message_box_S 115 and message_box_P 116. If for any reasoneither message box is compromised or out of service, another replacementor backup message box can be deployed immediately. In this invention,any key component, including router, network switch, message box, SmartDevice Client 109, or even Private Cloud Routing Server 108, can bereplaced without affecting the efficiency and integrity of thecommunication link between the Smart Device Client 109 and the PrivateCloud Routing Server 108.

FIG. 9 shows a block diagram of the Private Cloud Routing Server 108 inaccordance with the present invention. It includes a processor 900, RAM902, network interface 903, input/output (I/O) 904, and non-volatilestorage 905. The non-volatile storage 905 further contains an operatingsystem (OS) 909, device driver 908, and private cloud routing serverdriver 907.

The network interface 903 can connect to LAN, WAN or 3G/4G network. TheI/O 904 is for user interface to the outside world, includinginput/output devices such as keyboard, mouse, audio and video. Thenon-volatile storage 905 is loaded with necessary software including OSand various device drivers.

The Private Cloud Routing Server Driver 907 is deployed to communicatewith the corresponding Private Cloud Client Driver from the Smart DeviceClient 109. The Private Cloud Routing Server Driver 907 initiatesinvitation, processes the access request, and then sends acknowledgementback to the Smart Device Client 109. Later, it sends communicationrequest to the Smart Device Client 109 and opens a hole in its router inthe outgoing direction. Once the incoming request from the Smart DeviceClient reaches the opened hole, the two-way communication channel isbound together. The Private Cloud Routing Server Driver 907 can startsecure peer-to-peer communication with the Smart Device Client 109.

FIG. 10 shows a block diagram of the Smart Device Client 109 inaccordance with the present invention. The Smart Device Client 109includes a processor 1000, RAM 1002, network interface 1003,input/output (I/O) 1004, and non-volatile storage 1005. The non-volatilestorage 1005 further contains an operating system (OS) 1009, devicedriver 1008, and Private Cloud Client Driver 1007. The Smart DeviceClient 109 will also be loaded with Application Programs 1006 tocommunicate with the Private Cloud Routing Server 108. The networkinterface 1003 can connect to LAN, WAN or 3G/4G network.

The I/O 1004 is for user interface to the outside world, includinginput/output devices such as touch pad, audio and video. Thenon-volatile storage can be hard disk storage or flash based solid statedisk. Inside the non-volatile storage 1005, it is loaded with necessarysoftware including OS and device drivers. The Private Cloud ClientDriver 1007 is deployed to communicate with the corresponding PrivateCloud Routing Server Driver 907 from the Private Cloud Routing Server108. The Private Cloud Client Driver 1007 responds to server invitation,replies with the access request, and then accepts acknowledgement fromthe Private Cloud Routing Server 108. Later, it sends communicationrequest to the Private Cloud Routing Server 108 and opens a hole in itsrouter in the outgoing direction.

Once the incoming request from the Private Cloud Routing Server 108reaches the opened hole, the two-way communication channel is boundtogether. The Smart Device Client 109 can start secure peer-to-peercommunication with the Private Cloud Routing Server 108. The PrivateNetwork Service 128 is then manageable or accessible by the Smart DeviceClient through the Public Cloud 100. The wording or access or accessiblecovers the meaning of manage or manageable throughout the text.

For performance consideration, the Private Cloud Routing Server 108 andthe corresponding router Router_P 102 can be one entity in certainenvironment. In either case, any reachable Private Network Services bythe Private Cloud Routing Server 108 is accessible by the Smart DeviceClient through the Public Cloud 100.

Although the present invention has been described in accordance with theembodiments shown, one of ordinary skill in the art will readilyrecognize that there could be variations to the embodiments and thosevariations would be within the spirit and scope of the presentinvention. Accordingly, many modifications may be made by one ofordinary skill in the art without departing from the spirit and scope ofthe appended claims.

What is claimed is:
 1. A method for use with a public cloud network thatincludes a private cloud routing server, a private router, a privatenetwork service, and a smart device client, the method comprising:processing an initial setup of a private cloud routing server and asmart device client in a client server relationship, wherein the privatecloud routing server is associated with a server message box located ona public cloud network separate from the private cloud routing server,and wherein the smart device client is associated with a client messagebox located on the public cloud network separate from the smart deviceclient, the initial setup including: sending, by the private cloudrouting server, a session based invitation to the client message box ofthe smart device client, retrieving, by the smart device client, thesession based invitation of the private cloud routing server from theclient message box of the smart device client, validating, by the smartdevice client, the session based invitation, in response to validatingthe session based invitation, transmitting, by the smart device client,a session based access request that includes a public IP address and aprivate IP address of the smart device client to the server message boxof the private cloud routing server, retrieving, by the private cloudrouting server, the session based access request of the smart deviceclient from the server message box, validating, by the private cloudroutine server, the session based access request; in response to thevalidating the session based access request, registering, by the privatecloud routing server, the public IP address and the private IP addressof the smart device client to allow access to the private cloud routingserver by the smart device client, sending, by the private cloud routingserver, a session based acknowledgment with a public IP address and aprivate IP address of the private cloud routing server to the clientmessage box of the smart device client, and enabling the smart deviceclient to securely access a private network service via the public cloudnetwork after registration of the public and private IP address of theprivate cloud routing server; and connecting the private cloud routingserver and smart device client by at least one connection of: inresponse to the private IP address of the private cloud routing serverbeing in a same first Local Area Network (LAN) as the smart deviceclient, the smart device client directly connects to the private cloudrouting server using the private IP address of the private cloud routingserver, and in response to the private IP address of the private cloudroutine server not being in the same first LAN as the smart deviceclient, the smart device client connects through a first WAN to thepublic cloud network using the public IP address of the private cloudroutine server.
 2. The method of claim 1, further comprising: creatingand managing, by the private cloud routing server, an authorized clientlist including corresponding message box information of a plurality ofsmart device clients.
 3. The method of claim 2, wherein the initialsetup further includes: sending a communication request to the smartdevice client; punching a hole in the router to stay open for a pendingsmart device client response; waiting for the router to bind the networkconnection between the smart device client and the private cloud routingserver; routing incoming request from the smart device client to theprivate cloud routing server; establishing a secure peer-to-peercommunication with the smart device client; and enabling access of theprivate network service from the smart device client.
 4. The method ofclaim 2, wherein the initial setup further includes: retrieving thesession based invitation from the device message box; retrieving thesession based acknowledgement from the client message box; sending acommunication request to the private cloud routing server; punching ahole in a router to stay open pending the private cloud routing serverresponse; waiting for the router to bind a network connection throughthe router to a network between the private cloud routing server and thesmart device client; routing an incoming request from the private cloudrouting server to the smart device client; establishing a securepeer-to-peer communication with the private cloud routing server; andaccessing the private network service through the private cloud routingserver.
 5. The method of claim 4, wherein the initial setup furtherincludes: accessing the private cloud routing server; accessing theprivate cloud routing server behind a firewall with fixed or dynamic IPaddresses, wherein the smart device client requires no outside or publiccloud based routing server in a wide area network (WAN), requires noadditional router setup in a local area network (LAN), and establishes asecure peer-to-peer communication channel with the private cloud routingserver; and accessing the private network service through the privatecloud routing server.
 6. The method of claim 4, wherein the initialsetup further includes: accessing the private cloud routing server;accessing the private cloud routing server behind a firewall with fixedor dynamic IP addresses, wherein the smart device client requires nooutside or public cloud based routing server in a wide area network(WAN), requires no additional router setup in a local area network(LAN), and establishes a secure peer-to-peer communication channel withthe private cloud routing server; mapping a local physical I/O to avirtual private cloud routing server I/O; and accessing the privatenetwork service through the private cloud routing server.
 7. The methodof claim 2, wherein the initial setup further includes: retrieving thesession based invitation from the client message box; sending a sessionbased reply to the server message box; retrieving the session basedacknowledgement from the client message box; waiting for a private cloudrouting server response; binding a network connection to a networkbetween the private cloud routing server and the smart device client;routing an incoming request from the private cloud routing server to thesmart device client; establishing a secure peer-to-peer communicationwith the private cloud routing server; and accessing the private networkservice through the private cloud routing server.
 8. The method of claim7 wherein the initial setup further includes: accessing the privatecloud routing server; accessing the private cloud routing server behinda firewall with fixed or dynamic IP addresses, wherein the smart deviceclient requires no outside or public cloud based routing server in awide area network (WAN), requires no additional router setup in a localarea network (LAN), and establishes a secure peer-to-peer communicationwith the server; and accessing the private network service through theprivate cloud routing server.
 9. The method of claim 7, wherein theinitial setup further includes: accessing the private cloud routingserver; accessing the private cloud routing server behind a firewallwith fixed or dynamic IP addresses, wherein the smart device clientrequires no outside or public cloud based routing server in a wide areanetwork (WAN), requires no additional router setup in a local areanetwork (LAN), and establishes a secure peer-to-peer communication withthe server; mapping a local physical I/O to a virtual server I/O; andaccessing the private network service through the private cloud routingserver.
 10. A private cloud routing server, comprising: a computingdevice; a network connection through a router to a network; and aprogram when executed by the computing device enables the private cloudrouting server to: create and manage an authorized client list toaccommodate a plurality of smart device clients; send a session basedinvitation to a client message box of a smart device client of theplurality of smart device clients; retrieve a session based accessrequest of the smart device client from a server message box, wherein apublic IP address and a private IP address of both the private cloudrouting server and the smart device client is registered; send a sessionbased acknowledgement to the client message box of the smart deviceclient, wherein the session based acknowledgment includes a currentpublic IP address and a current private IP address of the private cloudrouting server; and enable access of private network services from thesmart device client; and connect the private cloud routing server andsmart device client by at least one connection of: in response to theprivate IP address of the private cloud routine server being in a samefirst Local Area Network (LAN) as the smart device client, the smartdevice client directly connects to the private cloud routine serverusing the private IP address of the private cloud routine server, and inresponse to the private IP address of the private cloud routine servernot being in the same first LAN as the smart device client, the smartdevice client connects through a first WAN to the public cloud networkusing the public IP address of the private cloud routing server.
 11. Asmart device client, comprising: a computing device; and a networkconnection through a router to a network, wherein the router has aprogram that in response to execution by the computing device enablesthe smart device client to: retrieve a session based invitation from asmart device client message box; send a session based access request toa private cloud routing server message box, wherein a public IP addressand a private IP address of both a private cloud routing server and thesmart device client is registered; retrieve a session basedacknowledgement from the smart device client message box, wherein thesession based acknowledgment includes a current public IP address and acurrent private IP address of the private cloud routing server; send acommunication request to the private cloud routing server; punch a holein the router to stay open pending a private cloud routing serverresponse; wait for the router to bind the network connection between theprivate cloud routing server and the smart device client; route anincoming request from the private cloud routing server to the smartdevice client; establish a secure peer-to-peer communication with theprivate cloud routing server; access a private network service throughthe private cloud routing server; and connect the private cloud routingserver and smart device client by at least one connection of: inresponse to the private IP address of the private cloud routing serverbeing in a same first Local Area Network (LAN) as the smart deviceclient, the smart device client directly connects to the private cloudrouting server using the private IP address of the private cloud routineserver, and in response to the private IP address of the private cloudroutine server not being in the same first LAN as the smart deviceclient, the smart device client connects through a first WAN to thepublic cloud network using the public IP address of the private cloudrouting server.